build(deps): bump cryptography from 46.0.5 to 50.0.0 in /tests - #9
build(deps): bump cryptography from 46.0.5 to 50.0.0 in /tests#9dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [cryptography](https://github.com/pyca/cryptography) from 46.0.5 to 50.0.0. - [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst) - [Commits](pyca/cryptography@46.0.5...50.0.0) --- updated-dependencies: - dependency-name: cryptography dependency-version: 50.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
LGTM — straightforward dependency bump.
What was reviewed: the change is a single-line version bump of cryptography (46.0.5 → 50.0.0) in requirements.txt for the tests directory, which is a transitive dependency needed for the community.crypto Ansible module. No code changes accompany this bump, and the new version includes a security fix (Bleichenbacher oracle timing leak in PKCS7 decryption) rather than introducing one.
Extended reasoning...
Overview
The PR touches a single line in tests/requirements.txt, bumping the cryptography pip package from 46.0.5 to 50.0.0. This is a Dependabot-generated dependency update with no application code changes. The dependency is used to support the community.crypto Ansible module in the test tooling, not in production cluster provisioning logic.
Security risks
No new security risks are introduced. The changelog for this major version bump actually includes a security fix (CVE-2026-69247, a Bleichenbacher-oracle timing/error leak in PKCS7 encryptedKey decryption), so this bump is defensive rather than risky. There is a large jump across major versions (46 → 50), which could theoretically introduce breaking API changes, but since this is only a test-tooling dependency and not vendored/used directly in kubespray's own source, the blast radius is limited to whether the test suite still runs correctly against the new version.
Level of scrutiny
This warrants minimal scrutiny — it is a routine, automated dependency bump confined to a test requirements file with no logic changes. It matches the 'simple, mechanical' category that doesn't need human review, similar to the pattern of prior dependency-bump commits already merged in this repo's history (e.g. the immediately preceding commit in the log bumping the same package).
Other factors
The bug-hunting system found no issues, and there are no unresolved review comments in the PR timeline. CI (if configured) would catch any incompatibility with the new major version during the test run itself.
Bumps cryptography from 46.0.5 to 50.0.0.
Changelog
Sourced from cryptography's changelog.
... (truncated)
Commits
dcb7050Prepare for 50.0.0 release (#15372)53fccd9Don't leak how PKCS#7 encryptedKey decryption failed (#15369)d472f97Addfrom __future__ import annotationsto all src/ Python files (#15371)908773dBump downstream dependencies in CI (#15368)2cc07ccBump BoringSSL, OpenSSL, AWS-LC in CI (#15367)c94ede9chore(deps): bump ruff from 0.16.0 to 0.16.1 (#15366)67a8308chore(deps): bump virtualenv from 21.7.0 to 21.7.1 (#15365)95018ffRelease the GIL in one-shot AEAD encrypt/decrypt (#15361)6954733Release the GIL during DH and DSA parameter generation (#15364)6893b94Import _serialization instead of serialization in x509/extensions (#15363)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.